Minimize shared-common everywhere#188606
Conversation
|
/ci |
78033e7 to
4688a67
Compare
0fcfca4 to
0ed5298
Compare
|
/ci |
|
/ci |
💔 Build Failed
Failed CI StepsHistory
cc @afharo |
|
/ci |
|
Pinging @elastic/security-detection-engine (Team:Detection Engine) |
|
Pinging @elastic/kibana-reporting-services (Team:Reporting Services) |
|
Pinging @elastic/kibana-esql (Team:ESQL) |
mykolaharmash
left a comment
There was a problem hiding this comment.
observability_onboarding changes LGTM ✨
tiansivive
left a comment
There was a problem hiding this comment.
LGTM from Security Entity Analytics
dmlemeshko
left a comment
There was a problem hiding this comment.
appex-qa changes LGTM
|
Thank you all for approving! Updating from |
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]Module Count
Public APIs missing comments
Any counts in public APIs
Public APIs missing exports
Page load bundle
Unknown metric groupsAPI count
ESLint disabled in files
ESLint disabled line counts
References to deprecated APIs
Total ESLint disabled count
History
To update your PR or re-run it, just comment with: cc @afharo |
Summary
At the moment, our package generator creates all packages with the type
shared-common. This means that we cannot enforce boundaries between server-side-only code and the browser, and vice-versa.packages/core/*src/core/type to be identified by thepluginpattern (publicandserverdirectories) vs. a package (either common, or single-scoped)commonlogic that shouldn't be so common 🙃For maintainers